-
Notifications
You must be signed in to change notification settings - Fork 217
test: use unique cluster name to avoid collisions #1479
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
test: use unique cluster name to avoid collisions #1479
Conversation
✅ Deploy Preview for kubernetes-sigs-cluster-api-gcp ready!
To edit notification comments on pull requests, go to your Netlify project configuration. |
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: salasberryfin The full list of commands accepted by this bot can be found here. The pull request process is described here
Needs approval from an approver in each of these files:
Approvers can indicate their approval by writing |
38d4c5c
to
dd33d16
Compare
Signed-off-by: Carlos Salas <[email protected]>
dd33d16
to
f17b52a
Compare
/retest |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
It works!
Thanks Carlos
/lgtm
/kind failing-test
What this PR does / why we need it:
Use unique cluster names for each test case to prevent name collisions. Reusing cluster resource names creates a situation where the
Cluster
object may be updated by a different cluster flavor, which may imply that the two definitions are not compatible and a webhook will disallow the change. Thanks @damdo for investigating and getting to the bottom of this.Which issue(s) this PR fixes:
Fixes #
Special notes for your reviewer:
The same change should be applied to GKE test cases. We can do that in the existing PR #1445, when we're ready to successfully run these tests.
TODOs:
Release note: